@cmoulliard what are the obstacles to use common buildah(-remote) task?

what are the obstacles to use common buildah(-remote) task?

What do you mean by "to use common buildah task" ? If the question is about: "Can we build the ubi builder image using buildah then the answer is no as such an image is not build from a Dockerfile by using a tool: pack - https://github.com/buildpacks/pack"

@cmoulliard have you considered running pack inside a build stage and just copying the content to the final stage?

have you considered running pack inside a build stage and just copying the content to the final stage?

What is a build stage ? Can you elaborate ?

What is a build stage ? Can you elaborate ?

Sorry for not being clear enough, I meant this

/verify-owners

Sorry for not being clear enough, I meant this

Thanks. We cannot use Dockerfile like Multi-stage to build the buildpack stuffs (builder image or stack image or buildpacks) but specific tools like: pack, jam, create-package, etc

/verify-owners

/retest

Can we merge it ?

Can we merge it ?

No, it has no approvals and unresolved threads

We have changed the ownership mechanism from OWNERS to CODEOWNERS. Please rebased on main and update CODEOWNERS instead of OWNERS 🙏

Please squash commits into one with nice description

Please squash commits into one with nice description

Done @MartinBasti

05e7400 this is not a nice description, in neither of commits. (Why it has 2 commits?)

https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/

(Why it has 2 commits?)

My fault. I missed one commit

PR needs rebase.

Label to rebase has been removed. Should I do then rebase ?

yes rebase, it won't hurt

yes rebase, it won't hurt

Sorry but I'm not a specialist to squash. If I git rebase -i HEAD~4, do next pick/squash, write/quit then I got a conflict with the renovate.js file which don't exist top of this PR ...

There seems no code conflict, then probably you can try these steps:

• update local main branch
• create a new branch
• cherry-pick the three commits in this PR
• force pushing to update this PR

There seems no code conflict, then probably you can try these steps:

I created a new branch containing the commits and merged them into one => https://github.com/redhat-buildpacks/fork-konflux-build-definitions/tree/new-paketo-builder
but I don't know how to push it on this PR. Can you help me ? @tkdchen

There seems no code conflict, then probably you can try these steps:

I created a new branch containing the commits and merged them into one => https://github.com/redhat-buildpacks/fork-konflux-build-definitions/tree/new-paketo-builder but I don't know how to push it on this PR. Can you help me ? @tkdchen

git checkout new-paketo-builder
git push --force HEAD:paketo-builder

❗ Before doing the force push, please ensure the new branch have all the necessary code because the force push will overwrite the paketo-builder branch completely.

❗ Before doing the force push, please ensure the new branch have all the necessary code because the force push will overwrite the paketo-builder branch completely.

I did a test successfully on konflux with the pipeline consuming the task of this PR from code pushed from the branch: new-paketo-builder @tkdchen

/retest

/retest